|
Software visualization〔Johannes Bohnet, Jürgen Döllner: ''Analyzing Feature Implementation by Visual Exploration of Architecturally-Embedded Call-Graphs''. 4th International Workshop on Dynamic Analysis, ACM, ACM Press, pp. 41–48, 2006.〕〔Diehl, 2002; Diehl, 2007; Knight, 2002)〕 or software visualisation refers to the visualization of information of and related to software systems -either the architecture of its source code or metrics of their runtime behavior- and their development process by means of static, interactive or animated 2-D or 3-D〔(Marcus et al., 2003; Wettel et al., 2007)〕 visual representations of their structure,〔(Staples & Bieman, 1999)〕 execution,〔J. Trümper et al.: ''Multiscale Visual Comparison of Execution Traces''. Proceedings of the International Conference on Program Comprehension, IEEE Computer Society, pp. 53-62, 2013.〕 behavior,〔(Kuhn et al., 2006, Stasko et al., 1997)〕 and evolution. == Software system information == Software visualization uses a variety of information available about software systems. Key information categories include: * implementation artifacts such as source codes, * software metric data from measurements or from reverse engineering, * traces that record execution behavior, * software testing data (e.g., test coverage) * software repository data that tracks changes. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「software visualization」の詳細全文を読む スポンサード リンク
|